Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44605832b93d6e84faa25c8327751d1b9ffc5ed54a1245f085ef5057006af77e

Tx prefix hash: a63f957bd098c8038e8284037adef28cb05c9a8d27f8df0339be6bb4b8993df6
Tx public key: 60b21993f1d61526a4272bb1e44e589b31213f48a8776e792cce920dd8c53abf
Timestamp: 1757208837 Timestamp [UCT]: 2025-09-07 01:33:57 Age [y:d:h:m:s]: 00:075:22:54:10
Block: 1363019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54288 RingCT/type: yes/0
Extra: 0160b21993f1d61526a4272bb1e44e589b31213f48a8776e792cce920dd8c53abf021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c9af5f7e79303cd1c165029af4ff1f4a9a13dfda0a991835c4b1af80a135922 0.600000000000 1851058 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": 1363029, "vin": [ { "gen": { "height": 1363019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c9af5f7e79303cd1c165029af4ff1f4a9a13dfda0a991835c4b1af80a135922" } } ], "extra": [ 1, 96, 178, 25, 147, 241, 214, 21, 38, 164, 39, 43, 177, 228, 78, 88, 155, 49, 33, 63, 72, 168, 119, 110, 121, 44, 206, 146, 13, 216, 197, 58, 191, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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