Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3f27c9acbccf79cd874fa7bf29cb14026c6b2586eff5e09194f7ff5cb01ef5b

Tx prefix hash: 022d7fb42ebe201a62b11698e8b38fc933cef364465ecc539fa4284afa6205c4
Tx public key: 2c663a1becc174600f92ebf09b2d6d1c8ae49813555cface6aea1dae7074cc3c
Timestamp: 1698525489 Timestamp [UCT]: 2023-10-28 20:38:09 Age [y:d:h:m:s]: 02:011:00:09:55
Block: 879736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527444 RingCT/type: yes/0
Extra: 012c663a1becc174600f92ebf09b2d6d1c8ae49813555cface6aea1dae7074cc3c02110000000b75e3f0e9000000000000000000

1 output(s) for total of 0.746568135000 dcy

stealth address amount amount idx
00: 0127bd6b533227ff1d316d5ad5f8cb8d08ae27e0e28773584e5f4d9ac2d7cdc2 0.746568135000 1335272 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": 879746, "vin": [ { "gen": { "height": 879736 } } ], "vout": [ { "amount": 746568135, "target": { "key": "0127bd6b533227ff1d316d5ad5f8cb8d08ae27e0e28773584e5f4d9ac2d7cdc2" } } ], "extra": [ 1, 44, 102, 58, 27, 236, 193, 116, 96, 15, 146, 235, 240, 155, 45, 109, 28, 138, 228, 152, 19, 85, 92, 250, 206, 106, 234, 29, 174, 112, 116, 204, 60, 2, 17, 0, 0, 0, 11, 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