Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32f189150a8c4fa4d1325b802a48c56b20bf4ba66ce13fd6dab6cdb746eab6b8

Tx prefix hash: 192992535bdd3a5726a01a08823407b465b69f5eab532b466cc0c8373fb8f8ab
Tx public key: 3e945de6b4bd38a894f82cb99282705862a272bae00cbc279a90c1bff1835a15
Timestamp: 1646773108 Timestamp [UCT]: 2022-03-08 20:58:28 Age [y:d:h:m:s]: 02:321:09:50:41
Block: 454228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 749173 RingCT/type: yes/0
Extra: 013e945de6b4bd38a894f82cb99282705862a272bae00cbc279a90c1bff1835a15021100000002bf7ee4e7000000000000000000

1 output(s) for total of 19.184670723000 dcy

stealth address amount amount idx
00: 64ac348e2f1280f94202d280005ef187921eaee8ff0736a9bd1c101f283465bd 19.184670723000 869835 of 0

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": 454238, "vin": [ { "gen": { "height": 454228 } } ], "vout": [ { "amount": 19184670723, "target": { "key": "64ac348e2f1280f94202d280005ef187921eaee8ff0736a9bd1c101f283465bd" } } ], "extra": [ 1, 62, 148, 93, 230, 180, 189, 56, 168, 148, 248, 44, 185, 146, 130, 112, 88, 98, 162, 114, 186, 224, 12, 188, 39, 154, 144, 193, 191, 241, 131, 90, 21, 2, 17, 0, 0, 0, 2, 191, 126, 228, 231, 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