Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10d6c7042e50b3176089c4d39f54750506fbc9d80746c0b0e80f481b2631c6b1

Tx prefix hash: 1d0b056a0665db24791e7a97ee16947670b2ff2deec3c0d4563b78c265d57b3f
Tx public key: 785fec356c92538a35ae03fc1a8daecac9bc0a05a45584ada609747803a1f87a
Timestamp: 1711513529 Timestamp [UCT]: 2024-03-27 04:25:29 Age [y:d:h:m:s]: 01:224:06:19:35
Block: 987220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418923 RingCT/type: yes/0
Extra: 01785fec356c92538a35ae03fc1a8daecac9bc0a05a45584ada609747803a1f87a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29f41191e8ed5cc55eae8b14e827a2ff2af2baf3f316787fc0840c7bc067b51c 0.600000000000 1447461 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": 987230, "vin": [ { "gen": { "height": 987220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29f41191e8ed5cc55eae8b14e827a2ff2af2baf3f316787fc0840c7bc067b51c" } } ], "extra": [ 1, 120, 95, 236, 53, 108, 146, 83, 138, 53, 174, 3, 252, 26, 141, 174, 202, 201, 188, 10, 5, 164, 85, 132, 173, 166, 9, 116, 120, 3, 161, 248, 122, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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