Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59210612b23985261f61212d959d1a015f0fe99670cd66553417eebe6b9c4da1

Tx prefix hash: 65d73ec16cdc128c191045037b1a850d101e14fb666aff5ffee39c29ace2bb1e
Tx public key: 2d3263d7c1e7f4dd458bc1f52ae02a4b1d161a7f9e21789651155a66f9118d2f
Timestamp: 1706608265 Timestamp [UCT]: 2024-01-30 09:51:05 Age [y:d:h:m:s]: 01:140:00:48:47
Block: 946512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361080 RingCT/type: yes/0
Extra: 012d3263d7c1e7f4dd458bc1f52ae02a4b1d161a7f9e21789651155a66f9118d2f0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3f73e301139646f6e658ddf08e3931a2fed07f69b8a7b0acc507e620aaa0a5 0.600000000000 1404844 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": 946522, "vin": [ { "gen": { "height": 946512 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3f73e301139646f6e658ddf08e3931a2fed07f69b8a7b0acc507e620aaa0a5" } } ], "extra": [ 1, 45, 50, 99, 215, 193, 231, 244, 221, 69, 139, 193, 245, 42, 224, 42, 75, 29, 22, 26, 127, 158, 33, 120, 150, 81, 21, 90, 102, 249, 17, 141, 47, 2, 17, 0, 0, 0, 4, 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