Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 445e1effc0d45a7ecbd6ab0b96756ad7bb44dc4f29d51e5a61d5d49dad84edc7

Tx prefix hash: 3ca4d6a7dad45c137536497f4c55964197e8c9ac27a3bfae464eb5994259b449
Tx public key: 1116261566741e02942c980581cd084dc6afa03c0b90384cc3fd1859dc2d665b
Timestamp: 1711458906 Timestamp [UCT]: 2024-03-26 13:15:06 Age [y:d:h:m:s]: 00:294:13:54:51
Block: 986772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210833 RingCT/type: yes/0
Extra: 011116261566741e02942c980581cd084dc6afa03c0b90384cc3fd1859dc2d665b0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a5c75d1f9dcec0bca1d53ff9c43161b35c12daf2e54813bc947d4cdc4a03f7b 0.600000000000 1447005 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": 986782, "vin": [ { "gen": { "height": 986772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a5c75d1f9dcec0bca1d53ff9c43161b35c12daf2e54813bc947d4cdc4a03f7b" } } ], "extra": [ 1, 17, 22, 38, 21, 102, 116, 30, 2, 148, 44, 152, 5, 129, 205, 8, 77, 198, 175, 160, 60, 11, 144, 56, 76, 195, 253, 24, 89, 220, 45, 102, 91, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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