Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e998f3b1bbad23b9039abe598c7bd1b3ac8c47dff5ccf7f6fcdecaf833425f

Tx prefix hash: 606d905dc2ad252e8c4e804772f37882c85096c83ef75dcdb20f94706328d375
Tx public key: a38e5981fd7f4bc8f4071f77df48e9f9be00af0384836254f75b63bf71b460b8
Timestamp: 1722789376 Timestamp [UCT]: 2024-08-04 16:36:16 Age [y:d:h:m:s]: 00:225:11:08:41
Block: 1080674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161039 RingCT/type: yes/0
Extra: 01a38e5981fd7f4bc8f4071f77df48e9f9be00af0384836254f75b63bf71b460b8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f73bcd6373ac772bc626ddbcee66d742592cb4996b02a6447b305a30cc4499d5 0.600000000000 1554123 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": 1080684, "vin": [ { "gen": { "height": 1080674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f73bcd6373ac772bc626ddbcee66d742592cb4996b02a6447b305a30cc4499d5" } } ], "extra": [ 1, 163, 142, 89, 129, 253, 127, 75, 200, 244, 7, 31, 119, 223, 72, 233, 249, 190, 0, 175, 3, 132, 131, 98, 84, 247, 91, 99, 191, 113, 180, 96, 184, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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