Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 372d905e90ede0d4cd6f7e8d0fa3a0490904e9bd0dd01e002275a78f5ccc16e8

Tx prefix hash: b51380fb04b6ba0ecf537b007ed2315be9073630e32defba884475b399822838
Tx public key: d144980636af15e0db7e68b1af7a5cfc71b8eb2740af8c7b222f349d67d2aeb5
Timestamp: 1714041561 Timestamp [UCT]: 2024-04-25 10:39:21 Age [y:d:h:m:s]: 01:001:22:33:57
Block: 1008153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262337 RingCT/type: yes/0
Extra: 01d144980636af15e0db7e68b1af7a5cfc71b8eb2740af8c7b222f349d67d2aeb502110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d2cb7412f4638e8c2beda4fc4f1b1fe72a822f04f801a956edaed885f655daf 0.600000000000 1469621 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": 1008163, "vin": [ { "gen": { "height": 1008153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d2cb7412f4638e8c2beda4fc4f1b1fe72a822f04f801a956edaed885f655daf" } } ], "extra": [ 1, 209, 68, 152, 6, 54, 175, 21, 224, 219, 126, 104, 177, 175, 122, 92, 252, 113, 184, 235, 39, 64, 175, 140, 123, 34, 47, 52, 157, 103, 210, 174, 181, 2, 17, 0, 0, 0, 6, 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