Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27bd3794476745cb96bbdbf036cee5a5cfe35b459b538649aa9812a32e542dad

Tx prefix hash: a4d729ac3645a35e581fd8bcb4c270b2cbce16abc39b629dc3ab8519b68a92c9
Tx public key: cf1c76c1947bb9b6eae8edb912c0c680f20bb82d513761793d12b83cc3d1032e
Timestamp: 1760157224 Timestamp [UCT]: 2025-10-11 04:33:44 Age [y:d:h:m:s]: 00:071:19:09:58
Block: 1387359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51413 RingCT/type: yes/0
Extra: 01cf1c76c1947bb9b6eae8edb912c0c680f20bb82d513761793d12b83cc3d1032e02110000000497baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1faede1319fa368fa7b791119fa295c1c8ec819bfd147cc90e9a861c41ba55d 0.600000000000 1875546 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": 1387369, "vin": [ { "gen": { "height": 1387359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1faede1319fa368fa7b791119fa295c1c8ec819bfd147cc90e9a861c41ba55d" } } ], "extra": [ 1, 207, 28, 118, 193, 148, 123, 185, 182, 234, 232, 237, 185, 18, 192, 198, 128, 242, 11, 184, 45, 81, 55, 97, 121, 61, 18, 184, 60, 195, 209, 3, 46, 2, 17, 0, 0, 0, 4, 151, 186, 249, 34, 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