Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5352073f392c35c19564f0591dd867480cb179dc21a35259f41d488302c3f692

Tx prefix hash: 5aedca5cba070e50a91b0aeb9277220e636293485d7c7ce26bee095052a827e4
Tx public key: 73efe9afa1af02e0e1236d00e00cb57a02430ecc31fba770d4c5eafbf6f30947
Timestamp: 1715452972 Timestamp [UCT]: 2024-05-11 18:42:52 Age [y:d:h:m:s]: 00:358:08:49:16
Block: 1019883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256146 RingCT/type: yes/0
Extra: 0173efe9afa1af02e0e1236d00e00cb57a02430ecc31fba770d4c5eafbf6f3094702110000000441ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f2d447d9a42bc9cab61f616658f80cbc6a51e1c32a5d2751313aba5e17922cb 0.600000000000 1483936 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": 1019893, "vin": [ { "gen": { "height": 1019883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f2d447d9a42bc9cab61f616658f80cbc6a51e1c32a5d2751313aba5e17922cb" } } ], "extra": [ 1, 115, 239, 233, 175, 161, 175, 2, 224, 225, 35, 109, 0, 224, 12, 181, 122, 2, 67, 14, 204, 49, 251, 167, 112, 212, 197, 234, 251, 246, 243, 9, 71, 2, 17, 0, 0, 0, 4, 65, 238, 28, 155, 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