Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb83299380146fa1a7d7ee5be0616aeec3541e3cb47f13f8dfbffb93ac38b4f7

Tx prefix hash: 25eff20caa1a860813c72bf07ca6e9cacd0939aed407232ebb525ef6c60bc1b6
Tx public key: 42ce2cac68f05195018acf539b0fb7026fbd0e667f36fefe3b7be855f1398614
Timestamp: 1714576313 Timestamp [UCT]: 2024-05-01 15:11:53 Age [y:d:h:m:s]: 00:341:01:56:55
Block: 1012591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243805 RingCT/type: yes/0
Extra: 0142ce2cac68f05195018acf539b0fb7026fbd0e667f36fefe3b7be855f139861402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9819b1f97de05d8b8fb6b20df6def5f14e8da2e1bea3f9753aac46b021bd26b 0.600000000000 1475167 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": 1012601, "vin": [ { "gen": { "height": 1012591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9819b1f97de05d8b8fb6b20df6def5f14e8da2e1bea3f9753aac46b021bd26b" } } ], "extra": [ 1, 66, 206, 44, 172, 104, 240, 81, 149, 1, 138, 207, 83, 155, 15, 183, 2, 111, 189, 14, 102, 127, 54, 254, 254, 59, 123, 232, 85, 241, 57, 134, 20, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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