Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 752f36ab13de970725b78b5958647e8be69ff3288207e324a9c24f7f9e7cc63e

Tx prefix hash: 92f8e3002d161ffece81b4c00a6703792fa5186fe60d6c6059dc1e2834da7946
Tx public key: 8d7bd0fe872d62c70acd784c0b31b7f778e1684c0dc7aafe79ec9538ac0f6ccd
Timestamp: 1711745868 Timestamp [UCT]: 2024-03-29 20:57:48 Age [y:d:h:m:s]: 01:221:04:53:05
Block: 989144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416737 RingCT/type: yes/0
Extra: 018d7bd0fe872d62c70acd784c0b31b7f778e1684c0dc7aafe79ec9538ac0f6ccd02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad156ed7f2f87e1645f41681148bb20878400294ffa0a98fb4d2c186e833abe8 0.600000000000 1449439 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": 989154, "vin": [ { "gen": { "height": 989144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad156ed7f2f87e1645f41681148bb20878400294ffa0a98fb4d2c186e833abe8" } } ], "extra": [ 1, 141, 123, 208, 254, 135, 45, 98, 199, 10, 205, 120, 76, 11, 49, 183, 247, 120, 225, 104, 76, 13, 199, 170, 254, 121, 236, 149, 56, 172, 15, 108, 205, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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