Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e82103752f8caf1f43c19f87a430093e941c27f5f215e791632b36c94db7565a

Tx prefix hash: 3a7f50339de0497838fe332d42436f9e923a6c35b8206229bbf503c9b5063e49
Tx public key: 521aa202b73149aa9b5a5bc04010d1d495e0587d1187ab2e77c02781ad056c12
Timestamp: 1734654105 Timestamp [UCT]: 2024-12-20 00:21:45 Age [y:d:h:m:s]: 00:107:05:41:48
Block: 1178958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76405 RingCT/type: yes/0
Extra: 01521aa202b73149aa9b5a5bc04010d1d495e0587d1187ab2e77c02781ad056c12021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81f3613a90657d957006c0c4bef95498b83d6681f0dbfc1ad69cf081ccfcf0a5 0.600000000000 1665349 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": 1178968, "vin": [ { "gen": { "height": 1178958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81f3613a90657d957006c0c4bef95498b83d6681f0dbfc1ad69cf081ccfcf0a5" } } ], "extra": [ 1, 82, 26, 162, 2, 183, 49, 73, 170, 155, 90, 91, 192, 64, 16, 209, 212, 149, 224, 88, 125, 17, 135, 171, 46, 119, 192, 39, 129, 173, 5, 108, 18, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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