Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 994c3b37107d822864ce698e3c6f217eeafd8ef5d6d2d76dc8ab30c76d2de4ee

Tx prefix hash: 4e6a86b3f5cb22b956eaa077181e67d0a5807f549efbb1ef05120c38a759daea
Tx public key: 472a06f5505bc49de2740224fc954a59a390f3afabb4f0865400bd3ae8a79ddf
Timestamp: 1716226135 Timestamp [UCT]: 2024-05-20 17:28:55 Age [y:d:h:m:s]: 01:170:18:41:29
Block: 1026278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380645 RingCT/type: yes/0
Extra: 01472a06f5505bc49de2740224fc954a59a390f3afabb4f0865400bd3ae8a79ddf02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 142ba08028ec74c80384caeb8793b1f3e5d9e2b48cb1c58ad7ae9c4631d45e72 0.600000000000 1493271 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": 1026288, "vin": [ { "gen": { "height": 1026278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "142ba08028ec74c80384caeb8793b1f3e5d9e2b48cb1c58ad7ae9c4631d45e72" } } ], "extra": [ 1, 71, 42, 6, 245, 80, 91, 196, 157, 226, 116, 2, 36, 252, 149, 74, 89, 163, 144, 243, 175, 171, 180, 240, 134, 84, 0, 189, 58, 232, 167, 157, 223, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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