Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2643e8dec35a45495b84873b596702022ac1c5a7f43bd60b0bf75b1e6f76c736

Tx prefix hash: bf9009bbede549be9d87ece8b4615a8696020536953c65c17ac8e63755db1309
Tx public key: 31638972756996a4907d99b791e252fe11a4c3e1b44ee9fb75fd85825f78a4a5
Timestamp: 1628954332 Timestamp [UCT]: 2021-08-14 15:18:52 Age [y:d:h:m:s]: 03:107:21:01:05
Block: 313965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 850301 RingCT/type: yes/0
Extra: 0131638972756996a4907d99b791e252fe11a4c3e1b44ee9fb75fd85825f78a4a5021100000002e6f80b5a000000000000000000

1 output(s) for total of 55.942523863000 dcy

stealth address amount amount idx
00: 2c942cf4e2b815b70f009a1f23a133c56538f06fe9d90a0a7a16810fa8854be4 55.942523863000 653486 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": 313975, "vin": [ { "gen": { "height": 313965 } } ], "vout": [ { "amount": 55942523863, "target": { "key": "2c942cf4e2b815b70f009a1f23a133c56538f06fe9d90a0a7a16810fa8854be4" } } ], "extra": [ 1, 49, 99, 137, 114, 117, 105, 150, 164, 144, 125, 153, 183, 145, 226, 82, 254, 17, 164, 195, 225, 180, 78, 233, 251, 117, 253, 133, 130, 95, 120, 164, 165, 2, 17, 0, 0, 0, 2, 230, 248, 11, 90, 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