Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38144ad76cf0989922e25b001b62d0ce6d7ebc5d9dc5c3dc27da563a4b6ebc28

Tx prefix hash: 907a925cba0581d0c0893a12268e091daf21caf9c2168a075e95f8d1d47bd8ec
Tx public key: 92f1607e3085393eb0b75688d68c68e9fd651ed64f08c621c54dfe9a13a1cdf9
Timestamp: 1724867710 Timestamp [UCT]: 2024-08-28 17:55:10 Age [y:d:h:m:s]: 00:287:02:46:59
Block: 1097906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205092 RingCT/type: yes/0
Extra: 0192f1607e3085393eb0b75688d68c68e9fd651ed64f08c621c54dfe9a13a1cdf9021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e9ec75f8714552c7551ea7588cfc76b4ca85d0ce354405d8101010930479251 0.600000000000 1573439 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": 1097916, "vin": [ { "gen": { "height": 1097906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e9ec75f8714552c7551ea7588cfc76b4ca85d0ce354405d8101010930479251" } } ], "extra": [ 1, 146, 241, 96, 126, 48, 133, 57, 62, 176, 183, 86, 136, 214, 140, 104, 233, 253, 101, 30, 214, 79, 8, 198, 33, 197, 77, 254, 154, 19, 161, 205, 249, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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