Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12b18ec654faca08a0810112078c91960b648793f411e3160b8aac809bf0f583

Tx prefix hash: d8a3919e1bb9f64aa13cb58a1d121346e62c854c5b35211fe94e76d27e96969f
Tx public key: d359d7338dc6699855caf99d8a4ceb23361131ca8b171c2940edc9ac9e0a0f2c
Timestamp: 1703066224 Timestamp [UCT]: 2023-12-20 09:57:04 Age [y:d:h:m:s]: 01:149:07:57:12
Block: 917161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367885 RingCT/type: yes/0
Extra: 01d359d7338dc6699855caf99d8a4ceb23361131ca8b171c2940edc9ac9e0a0f2c021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00b6c155f0380485df8f43bf5f453b48de085c5be17bd1bb606deb156a1b52a4 0.600000000000 1374731 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": 917171, "vin": [ { "gen": { "height": 917161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00b6c155f0380485df8f43bf5f453b48de085c5be17bd1bb606deb156a1b52a4" } } ], "extra": [ 1, 211, 89, 215, 51, 141, 198, 105, 152, 85, 202, 249, 157, 138, 76, 235, 35, 54, 17, 49, 202, 139, 23, 28, 41, 64, 237, 201, 172, 158, 10, 15, 44, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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