Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10de7e1d83f03178a797c84c0ce8f112a2a5c86a6377c3568cd62048e1aee95a

Tx prefix hash: 22e7b69568f13373aa4f7236faddade932dacea48d4ed5684b393eab142b15b7
Tx public key: f2dbb608e255b25ad1b19d70b452cb68bd520e0301314ecde110a97d331f8dfb
Timestamp: 1702376752 Timestamp [UCT]: 2023-12-12 10:25:52 Age [y:d:h:m:s]: 01:358:11:35:56
Block: 911465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515097 RingCT/type: yes/0
Extra: 01f2dbb608e255b25ad1b19d70b452cb68bd520e0301314ecde110a97d331f8dfb02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a2dde2e17f49b1b22b2f6d76eee5d54d89a6dd396172893e8a7fd4122deaa93 0.600000000000 1368669 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": 911475, "vin": [ { "gen": { "height": 911465 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a2dde2e17f49b1b22b2f6d76eee5d54d89a6dd396172893e8a7fd4122deaa93" } } ], "extra": [ 1, 242, 219, 182, 8, 226, 85, 178, 90, 209, 177, 157, 112, 180, 82, 203, 104, 189, 82, 14, 3, 1, 49, 78, 205, 225, 16, 169, 125, 51, 31, 141, 251, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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