Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba6498b2614120b53563edf31638bc5cf7aea3799727ade1b04655b1a1f409bf

Tx prefix hash: 663ddb473cbb6ad134b846c1b625bb263670f5b81f1b761d6bee2cefaa5c67d8
Tx public key: 6d4e39c409b0e5520ef27fe0b9d310c08434b2a72a561d93683d34554f785673
Timestamp: 1681694062 Timestamp [UCT]: 2023-04-17 01:14:22 Age [y:d:h:m:s]: 01:360:03:41:11
Block: 740218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 518694 RingCT/type: yes/0
Extra: 016d4e39c409b0e5520ef27fe0b9d310c08434b2a72a561d93683d34554f78567302110000000375e3f0e9000000000000000000

1 output(s) for total of 2.164465682000 dcy

stealth address amount amount idx
00: 39a81b40966384cdbcfe422d1aa225c0b220b79814d7e3a3f979aa445f136f16 2.164465682000 1187103 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": 740228, "vin": [ { "gen": { "height": 740218 } } ], "vout": [ { "amount": 2164465682, "target": { "key": "39a81b40966384cdbcfe422d1aa225c0b220b79814d7e3a3f979aa445f136f16" } } ], "extra": [ 1, 109, 78, 57, 196, 9, 176, 229, 82, 14, 242, 127, 224, 185, 211, 16, 192, 132, 52, 178, 167, 42, 86, 29, 147, 104, 61, 52, 85, 79, 120, 86, 115, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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