Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e127f76e94a94de957ee3899dcb06b76c16cf2e326cb9265d10d9892454f8b52

Tx prefix hash: bf47be6de318e9021d6a60413392b3ccd9d5829837a7c42f9faa47b34f18273e
Tx public key: 872811844e464755e7ba9cf15e070923724cd109766e01c9a3e1f3d7f7efdaa4
Timestamp: 1691100570 Timestamp [UCT]: 2023-08-03 22:09:30 Age [y:d:h:m:s]: 02:102:14:16:34
Block: 818229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592998 RingCT/type: yes/0
Extra: 01872811844e464755e7ba9cf15e070923724cd109766e01c9a3e1f3d7f7efdaa402110000000575e3f0e9000000000000000000

1 output(s) for total of 1.193624606000 dcy

stealth address amount amount idx
00: cd34d9845eaf920d75ca3eea4f879290570c2fc13fd72f94ae219038612e4f30 1.193624606000 1270171 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": 818239, "vin": [ { "gen": { "height": 818229 } } ], "vout": [ { "amount": 1193624606, "target": { "key": "cd34d9845eaf920d75ca3eea4f879290570c2fc13fd72f94ae219038612e4f30" } } ], "extra": [ 1, 135, 40, 17, 132, 78, 70, 71, 85, 231, 186, 156, 241, 94, 7, 9, 35, 114, 76, 209, 9, 118, 110, 1, 201, 163, 225, 243, 215, 247, 239, 218, 164, 2, 17, 0, 0, 0, 5, 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