Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2c3bae6abab682c584e76b40a7db3ed5438540784f6811045a6129b7a03f6f2

Tx prefix hash: 1a4b7fc5da70e3a9ab95b15d56f8af4bbf38015cfce90d6c51452a2623f683ef
Tx public key: 1ca8cd36b59fb77f4930d0abfbf7d32237a25d6e7cd8027bce1099ffefd418fe
Timestamp: 1710449222 Timestamp [UCT]: 2024-03-14 20:47:02 Age [y:d:h:m:s]: 01:238:15:07:57
Block: 978397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429226 RingCT/type: yes/0
Extra: 011ca8cd36b59fb77f4930d0abfbf7d32237a25d6e7cd8027bce1099ffefd418fe0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07cade463d9dc727e244dc5d9624d8881863d56de97e4945690c4aa595843241 0.600000000000 1438424 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": 978407, "vin": [ { "gen": { "height": 978397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07cade463d9dc727e244dc5d9624d8881863d56de97e4945690c4aa595843241" } } ], "extra": [ 1, 28, 168, 205, 54, 181, 159, 183, 127, 73, 48, 208, 171, 251, 247, 211, 34, 55, 162, 93, 110, 124, 216, 2, 123, 206, 16, 153, 255, 239, 212, 24, 254, 2, 17, 0, 0, 0, 3, 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