Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b475845de8e066e36db8834bf76d1631e15c902072a9878765decda063f3a9

Tx prefix hash: 2649234a5f475f6a42c946e4af4404a2dbdeaa1f126ada10825ec75133b8f390
Tx public key: 088b97b79e02936a5c8ccd0358b9f4861bc328f5c2ad7a2818b9c45efafbbad1
Timestamp: 1702673320 Timestamp [UCT]: 2023-12-15 20:48:40 Age [y:d:h:m:s]: 01:104:10:14:32
Block: 913907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335762 RingCT/type: yes/0
Extra: 01088b97b79e02936a5c8ccd0358b9f4861bc328f5c2ad7a2818b9c45efafbbad102110000000133af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9dc2e62b303d79f25999aeb4b96f5ae0274eb1cf370157a7ff2985677ea4dec 0.600000000000 1371187 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": 913917, "vin": [ { "gen": { "height": 913907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9dc2e62b303d79f25999aeb4b96f5ae0274eb1cf370157a7ff2985677ea4dec" } } ], "extra": [ 1, 8, 139, 151, 183, 158, 2, 147, 106, 92, 140, 205, 3, 88, 185, 244, 134, 27, 195, 40, 245, 194, 173, 122, 40, 24, 185, 196, 94, 250, 251, 186, 209, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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