Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec1953cc947a8876ec4e4c7791e6dd3d0a42b6c27ad1d3db878c502ecb839bb5

Tx prefix hash: ddcd6fd7836f737895427a1de80b6765743019c71a8aff65f270df921daffe85
Tx public key: a1b4d8d782f131da1d405616fb310ce41b109d60b417f71f2b798d9ef83d32c5
Timestamp: 1578039796 Timestamp [UCT]: 2020-01-03 08:23:16 Age [y:d:h:m:s]: 05:302:21:09:07
Block: 37613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1364117 RingCT/type: yes/0
Extra: 01a1b4d8d782f131da1d405616fb310ce41b109d60b417f71f2b798d9ef83d32c50211000000a5410370dd000000000000000000

1 output(s) for total of 460.652431876000 dcy

stealth address amount amount idx
00: 8bbe6e6974bc5c203989c46415b167a444f1dc01a9871096a5cc6d58d170a479 460.652431876000 63937 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": 37623, "vin": [ { "gen": { "height": 37613 } } ], "vout": [ { "amount": 460652431876, "target": { "key": "8bbe6e6974bc5c203989c46415b167a444f1dc01a9871096a5cc6d58d170a479" } } ], "extra": [ 1, 161, 180, 216, 215, 130, 241, 49, 218, 29, 64, 86, 22, 251, 49, 12, 228, 27, 16, 157, 96, 180, 23, 247, 31, 43, 121, 141, 158, 248, 61, 50, 197, 2, 17, 0, 0, 0, 165, 65, 3, 112, 221, 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