Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af85e42a82856c6b43ba3b4c7ec8e838001fe1392e69c6de2754e464f1344a31

Tx prefix hash: 3ed6b7f985297bb1ea20d6af0436dcd028a42821e5ab24ee044c4f368a0e85fd
Tx public key: d35d1630efa05e4f0668b0246848bcd8d17202dcc776ee873b9829719446a41f
Timestamp: 1634962124 Timestamp [UCT]: 2021-10-23 04:08:44 Age [y:d:h:m:s]: 04:009:11:56:34
Block: 358559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1043477 RingCT/type: yes/0
Extra: 01d35d1630efa05e4f0668b0246848bcd8d17202dcc776ee873b9829719446a41f021100000002f60c5d7e000000000000000000

1 output(s) for total of 39.807110573000 dcy

stealth address amount amount idx
00: 9ea7d67fbbed3e4430a8d8346fe25f5da3c050762af82c26a26e417ab86ac219 39.807110573000 730546 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": 358569, "vin": [ { "gen": { "height": 358559 } } ], "vout": [ { "amount": 39807110573, "target": { "key": "9ea7d67fbbed3e4430a8d8346fe25f5da3c050762af82c26a26e417ab86ac219" } } ], "extra": [ 1, 211, 93, 22, 48, 239, 160, 94, 79, 6, 104, 176, 36, 104, 72, 188, 216, 209, 114, 2, 220, 199, 118, 238, 135, 59, 152, 41, 113, 148, 70, 164, 31, 2, 17, 0, 0, 0, 2, 246, 12, 93, 126, 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