Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cba5d1fc74158d54a15e34c8045b4d240e4bc0e32e913d36f7200fb7cdd0ea11

Tx prefix hash: 89aa547e494ebd9506d72c65409cdce2715fc1d4e5f38b8ee4d57acac268c96e
Tx public key: 9163df9f9208808a8d37a49fd468a97ccadd8ae929f0d2c2a835493cdb4619ac
Timestamp: 1715658170 Timestamp [UCT]: 2024-05-14 03:42:50 Age [y:d:h:m:s]: 00:288:09:12:35
Block: 1021561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206106 RingCT/type: yes/0
Extra: 019163df9f9208808a8d37a49fd468a97ccadd8ae929f0d2c2a835493cdb4619ac0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c338f9dc049bf3676e9f268ac3eabe918176bfd58466fca4223593034cd2b999 0.600000000000 1485916 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": 1021571, "vin": [ { "gen": { "height": 1021561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c338f9dc049bf3676e9f268ac3eabe918176bfd58466fca4223593034cd2b999" } } ], "extra": [ 1, 145, 99, 223, 159, 146, 8, 128, 138, 141, 55, 164, 159, 212, 104, 169, 124, 202, 221, 138, 233, 41, 240, 210, 194, 168, 53, 73, 60, 219, 70, 25, 172, 2, 17, 0, 0, 0, 1, 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