Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 377409a550d7d1c5800867a48ef7a5d7e9ef38f000000dd8820cbbbee880ab6a

Tx prefix hash: 4e7952c8a4653cdfe4a6eb994b3b66b1e26cc01a6e85cfd4659b4a7fe6c00c99
Tx public key: b4c7f66fa47fe3a152b27a998034ab2c7389fc06bf7d9507e84295a51a8cf769
Timestamp: 1758824422 Timestamp [UCT]: 2025-09-25 18:20:22 Age [y:d:h:m:s]: 00:012:04:27:27
Block: 1376322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8707 RingCT/type: yes/0
Extra: 01b4c7f66fa47fe3a152b27a998034ab2c7389fc06bf7d9507e84295a51a8cf76902110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ba6bc7ac80d0533ea1626df84876fbd461f33694da2edbcca21ae202c8f7ad6 0.600000000000 1864413 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": 1376332, "vin": [ { "gen": { "height": 1376322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ba6bc7ac80d0533ea1626df84876fbd461f33694da2edbcca21ae202c8f7ad6" } } ], "extra": [ 1, 180, 199, 246, 111, 164, 127, 227, 161, 82, 178, 122, 153, 128, 52, 171, 44, 115, 137, 252, 6, 191, 125, 149, 7, 232, 66, 149, 165, 26, 140, 247, 105, 2, 17, 0, 0, 0, 2, 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