Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eb87b7f2bf5a8d42c8b3853814669be01027e7c204635dfd5499520fa49a49a

Tx prefix hash: 8a74f6f81e9f5a7f867baa29e84256d158cdf9a2f4db2cc2cae4157714b6d948
Tx public key: bbe6c916af1726f1bbfa55f6ab3522d60e0a622035d26b0385aacb61375ed9c2
Timestamp: 1751543941 Timestamp [UCT]: 2025-07-03 11:59:01 Age [y:d:h:m:s]: 00:141:01:54:09
Block: 1317913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99075 RingCT/type: yes/0
Extra: 01bbe6c916af1726f1bbfa55f6ab3522d60e0a622035d26b0385aacb61375ed9c202110000001543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9d7ba1a9ae0bd5139c4d85b61c74ac01e0dd86263c2b3b8e545e452f628bfb5 0.600000000000 1805584 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": 1317923, "vin": [ { "gen": { "height": 1317913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9d7ba1a9ae0bd5139c4d85b61c74ac01e0dd86263c2b3b8e545e452f628bfb5" } } ], "extra": [ 1, 187, 230, 201, 22, 175, 23, 38, 241, 187, 250, 85, 246, 171, 53, 34, 214, 14, 10, 98, 32, 53, 210, 107, 3, 133, 170, 203, 97, 55, 94, 217, 194, 2, 17, 0, 0, 0, 21, 67, 132, 109, 102, 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