Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17c93cef46a97186d2f5b709f71d365f7f0a84bbdd1db4e80062d1e1cc0e519c

Tx prefix hash: c76747f558edc013a8114d3b78fddca486ecfd611d72deee413e71a6648495e2
Tx public key: 67843678e2a4613504b431e348dc1e8fa74e885f45c4fb99acbe7b54e585757c
Timestamp: 1710987068 Timestamp [UCT]: 2024-03-21 02:11:08 Age [y:d:h:m:s]: 01:235:12:10:58
Block: 982851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426996 RingCT/type: yes/0
Extra: 0167843678e2a4613504b431e348dc1e8fa74e885f45c4fb99acbe7b54e585757c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f072863293402238a30c7a9900a85da0c9d78c47269dfbe969dcf31c866917f9 0.600000000000 1442964 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": 982861, "vin": [ { "gen": { "height": 982851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f072863293402238a30c7a9900a85da0c9d78c47269dfbe969dcf31c866917f9" } } ], "extra": [ 1, 103, 132, 54, 120, 226, 164, 97, 53, 4, 180, 49, 227, 72, 220, 30, 143, 167, 78, 136, 95, 69, 196, 251, 153, 172, 190, 123, 84, 229, 133, 117, 124, 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