Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 170206a48f9463c3ee542780b403fec68f5c11b5ade454e04d8df32a0617aef1

Tx prefix hash: d0ab84e73f2407a49fa86731236fada034baf2e85754cb0a746a6f4a05244383
Tx public key: df77d4dc863b7c453ab1a7c9b4c90a9776d28c725bc39ef8c6380db076cfae8d
Timestamp: 1726583008 Timestamp [UCT]: 2024-09-17 14:23:28 Age [y:d:h:m:s]: 00:074:22:06:03
Block: 1112130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53572 RingCT/type: yes/0
Extra: 01df77d4dc863b7c453ab1a7c9b4c90a9776d28c725bc39ef8c6380db076cfae8d02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29cb14601cc4b94bfa8927a64ff51d28218f0c14772d0097f88a5860078c70dc 0.600000000000 1591343 of 15

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": 1112140, "vin": [ { "gen": { "height": 1112130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29cb14601cc4b94bfa8927a64ff51d28218f0c14772d0097f88a5860078c70dc" } } ], "extra": [ 1, 223, 119, 212, 220, 134, 59, 124, 69, 58, 177, 167, 201, 180, 201, 10, 151, 118, 210, 140, 114, 91, 195, 158, 248, 198, 56, 13, 176, 118, 207, 174, 141, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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