Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e443eb5544fa8243845fda23ae0d9046a8975d1a1d93442d672db9bab0ba0d

Tx prefix hash: ba73495edb62d188d5384efb63dcecb6d38b2fbf5790cfdc2a4eb33af9950729
Tx public key: f2ad7f7877a0112ed2cfe10559850d6c06def38ef1b51af7c99fa0b7dcd0a3fb
Timestamp: 1737337811 Timestamp [UCT]: 2025-01-20 01:50:11 Age [y:d:h:m:s]: 00:304:20:29:48
Block: 1201098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215431 RingCT/type: yes/0
Extra: 01f2ad7f7877a0112ed2cfe10559850d6c06def38ef1b51af7c99fa0b7dcd0a3fb02110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a49e8e43e2b83264628fe4fc35ecbb23af8ebebbff8519f238b4be7664fa8be 0.600000000000 1687747 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": 1201108, "vin": [ { "gen": { "height": 1201098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a49e8e43e2b83264628fe4fc35ecbb23af8ebebbff8519f238b4be7664fa8be" } } ], "extra": [ 1, 242, 173, 127, 120, 119, 160, 17, 46, 210, 207, 225, 5, 89, 133, 13, 108, 6, 222, 243, 142, 241, 181, 26, 247, 201, 159, 160, 183, 220, 208, 163, 251, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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