Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9be0227c543d4e57431bdef7a2a26359a0fa1ce660b2a15195d0f8956ced1440

Tx prefix hash: 1b8af3baa4af57f4556940b0d4664ece3a5a2c200b15ef65e32eb37da0ed1285
Tx public key: 90a725612a4fe8e64ecb0714e6ffe5d3b4bb2274ecc5bce461d8459d3c129caf
Timestamp: 1727449177 Timestamp [UCT]: 2024-09-27 14:59:37 Age [y:d:h:m:s]: 00:105:16:44:31
Block: 1119319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75565 RingCT/type: yes/0
Extra: 0190a725612a4fe8e64ecb0714e6ffe5d3b4bb2274ecc5bce461d8459d3c129caf02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 514e79c81e61d7c5f30d3724ff413dbaaae8bd88b92b57b111517f8cc2a3e83e 0.600000000000 1600834 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": 1119329, "vin": [ { "gen": { "height": 1119319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "514e79c81e61d7c5f30d3724ff413dbaaae8bd88b92b57b111517f8cc2a3e83e" } } ], "extra": [ 1, 144, 167, 37, 97, 42, 79, 232, 230, 78, 203, 7, 20, 230, 255, 229, 211, 180, 187, 34, 116, 236, 197, 188, 228, 97, 216, 69, 157, 60, 18, 156, 175, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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