Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 37ae5b19d701694774a897e23aefce451c0152c1892270c8c2e74f327a32e1ec

Tx prefix hash: 49e4f1b81bd63dd69bacf3873b168478e130f7167645a8b5b4c33c93825a77b0
Tx public key: 84b52239efd5048f225e5284a0415efb9318e09b43081c3e6bed3eaeb875f51f
Timestamp: 1758826364 Timestamp [UCT]: 2025-09-25 18:52:44 Age [y:d:h:m:s]: 00:012:04:38:22
Block: 1376336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8718 RingCT/type: yes/0
Extra: 0184b52239efd5048f225e5284a0415efb9318e09b43081c3e6bed3eaeb875f51f02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bee929ad12f746acf3c85eeacf215b1bef66b435ff1641cfbd59ebcc782e6d35 0.600000000000 1864427 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1376346, "vin": [ { "gen": { "height": 1376336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bee929ad12f746acf3c85eeacf215b1bef66b435ff1641cfbd59ebcc782e6d35" } } ], "extra": [ 1, 132, 181, 34, 57, 239, 213, 4, 143, 34, 94, 82, 132, 160, 65, 94, 251, 147, 24, 224, 155, 67, 8, 28, 62, 107, 237, 62, 174, 184, 117, 245, 31, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8