Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec61cc92896ccd72c191576348d1d558ac9077d02713a98bceae49222f60d1f1

Tx prefix hash: df829445226f785f44f37ccd1a8b3812dbef314d37f6f46dee25b19ac1ce3571
Tx public key: 2dfa025689fd7f00d3414b6646ee76dc64b56c48a0e91097206d5a4aa625552a
Timestamp: 1658979623 Timestamp [UCT]: 2022-07-28 03:40:23 Age [y:d:h:m:s]: 03:129:19:03:57
Block: 553288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 872570 RingCT/type: yes/0
Extra: 012dfa025689fd7f00d3414b6646ee76dc64b56c48a0e91097206d5a4aa625552a02110000000dd834ebe0000000000000000000

1 output(s) for total of 9.010052109000 dcy

stealth address amount amount idx
00: 80031d3246d2154c37c0e624585b7b54a60d40fbf65b2974ee0c13a2bb970d52 9.010052109000 985068 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": 553298, "vin": [ { "gen": { "height": 553288 } } ], "vout": [ { "amount": 9010052109, "target": { "key": "80031d3246d2154c37c0e624585b7b54a60d40fbf65b2974ee0c13a2bb970d52" } } ], "extra": [ 1, 45, 250, 2, 86, 137, 253, 127, 0, 211, 65, 75, 102, 70, 238, 118, 220, 100, 181, 108, 72, 160, 233, 16, 151, 32, 109, 90, 74, 166, 37, 85, 42, 2, 17, 0, 0, 0, 13, 216, 52, 235, 224, 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