Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c944933740e7d4281f8a6d69dc38e8f0bc8363de1510a561a6bde9de4327f9eb

Tx prefix hash: cfcfe5d4863e90a3eaa6c66393c5c6a013fdb8ef0990eb873adb8519fa457734
Tx public key: 5bbc1aa4d0ac1c91f131f3f6070f2ebb505319a01ce9075f14250ff88497ebc4
Timestamp: 1715832835 Timestamp [UCT]: 2024-05-16 04:13:55 Age [y:d:h:m:s]: 00:332:14:54:54
Block: 1023013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237751 RingCT/type: yes/0
Extra: 015bbc1aa4d0ac1c91f131f3f6070f2ebb505319a01ce9075f14250ff88497ebc402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58c80608a455303990792097fd76ad8f363fe4de850c3705f6a7b162d3b68b5 0.600000000000 1487780 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": 1023023, "vin": [ { "gen": { "height": 1023013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58c80608a455303990792097fd76ad8f363fe4de850c3705f6a7b162d3b68b5" } } ], "extra": [ 1, 91, 188, 26, 164, 208, 172, 28, 145, 241, 49, 243, 246, 7, 15, 46, 187, 80, 83, 25, 160, 28, 233, 7, 95, 20, 37, 15, 248, 132, 151, 235, 196, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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