Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1e9b339ea2bd77849ef1eb7568bdd4d2b9082de5246780df96c495720642eb

Tx prefix hash: 9122b376e60fd408f298bf0e27c3f022c8bda6e8519a6106921e20b4da2f0817
Tx public key: 1a38fbeeeaca7e1afd3a04ce919266a3a1d19ff4e93d44cf353a549598707aae
Timestamp: 1714210418 Timestamp [UCT]: 2024-04-27 09:33:38 Age [y:d:h:m:s]: 01:051:16:34:55
Block: 1009555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297794 RingCT/type: yes/0
Extra: 011a38fbeeeaca7e1afd3a04ce919266a3a1d19ff4e93d44cf353a549598707aae0211000000120011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34d0fcce8a2a66a0b2f0f55e1a22f46ea1057b767b7355bf6ef8ec829cab084a 0.600000000000 1471263 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": 1009565, "vin": [ { "gen": { "height": 1009555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34d0fcce8a2a66a0b2f0f55e1a22f46ea1057b767b7355bf6ef8ec829cab084a" } } ], "extra": [ 1, 26, 56, 251, 238, 234, 202, 126, 26, 253, 58, 4, 206, 145, 146, 102, 163, 161, 209, 159, 244, 233, 61, 68, 207, 53, 58, 84, 149, 152, 112, 122, 174, 2, 17, 0, 0, 0, 18, 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