Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31a0c55561c40701ae91a8392fa17fb7a2a1b3786c444cc0903f40ac941f8507

Tx prefix hash: 774f7640f0cb2f11f6ed92ab3d585a6ededd7ca7a9293c9b083a420f41798c46
Tx public key: 372100c1dfb3ec8305009d2b2544a703217a442c9dbdc5550414d383179fbab0
Timestamp: 1706512528 Timestamp [UCT]: 2024-01-29 07:15:28 Age [y:d:h:m:s]: 01:049:13:24:30
Block: 945715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296509 RingCT/type: yes/0
Extra: 01372100c1dfb3ec8305009d2b2544a703217a442c9dbdc5550414d383179fbab00211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79463b92242e8dc3797eadb77b8358f35d871c1b231f3b8f53e9666f6c60245c 0.600000000000 1404033 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": 945725, "vin": [ { "gen": { "height": 945715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79463b92242e8dc3797eadb77b8358f35d871c1b231f3b8f53e9666f6c60245c" } } ], "extra": [ 1, 55, 33, 0, 193, 223, 179, 236, 131, 5, 0, 157, 43, 37, 68, 167, 3, 33, 122, 68, 44, 157, 189, 197, 85, 4, 20, 211, 131, 23, 159, 186, 176, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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