Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e6789f7b92d4c3c4f84be70066424c16028a680c157c48684c8f63c1cb68467

Tx prefix hash: 6c017cc1e084cdf839bee73676ae607bbca8bbc0161b42c58c2a53e788434fbb
Tx public key: fa36afec0672daf12910ddb78d4c0495ce9083f7a716e3b0e167a8694e2c1f2c
Timestamp: 1717937178 Timestamp [UCT]: 2024-06-09 12:46:18 Age [y:d:h:m:s]: 00:301:12:23:21
Block: 1040453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215468 RingCT/type: yes/0
Extra: 01fa36afec0672daf12910ddb78d4c0495ce9083f7a716e3b0e167a8694e2c1f2c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee9ab9f4cbb4e47729d33c8f455987c9e205b702bf91131a31511c1cc68ff926 0.600000000000 1509110 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": 1040463, "vin": [ { "gen": { "height": 1040453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee9ab9f4cbb4e47729d33c8f455987c9e205b702bf91131a31511c1cc68ff926" } } ], "extra": [ 1, 250, 54, 175, 236, 6, 114, 218, 241, 41, 16, 221, 183, 141, 76, 4, 149, 206, 144, 131, 247, 167, 22, 227, 176, 225, 103, 168, 105, 78, 44, 31, 44, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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