Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33f68107dfd65f116c33ba4af69ebcac6b7867fc03819de7461eb33215110fb1

Tx prefix hash: 8707f88c8e3831cb2537f05aa3353efe6d9f6cea6832aa4116346a3d93c25245
Tx public key: 9ecc97e5c7fdbab83bc0ccf5bc754d80eeb04a2a0b3bbe9cdb03170af5446972
Timestamp: 1701532528 Timestamp [UCT]: 2023-12-02 15:55:28 Age [y:d:h:m:s]: 01:049:11:04:13
Block: 904444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296687 RingCT/type: yes/0
Extra: 019ecc97e5c7fdbab83bc0ccf5bc754d80eeb04a2a0b3bbe9cdb03170af5446972021100000003e08532b6000000000000000000

1 output(s) for total of 0.618303283000 dcy

stealth address amount amount idx
00: c951a0abbe7ef26af2bf701937148f3e1f3a2b2c55471646d1c65ecc53bb6535 0.618303283000 1361199 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": 904454, "vin": [ { "gen": { "height": 904444 } } ], "vout": [ { "amount": 618303283, "target": { "key": "c951a0abbe7ef26af2bf701937148f3e1f3a2b2c55471646d1c65ecc53bb6535" } } ], "extra": [ 1, 158, 204, 151, 229, 199, 253, 186, 184, 59, 192, 204, 245, 188, 117, 77, 128, 238, 176, 74, 42, 11, 59, 190, 156, 219, 3, 23, 10, 245, 68, 105, 114, 2, 17, 0, 0, 0, 3, 224, 133, 50, 182, 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