Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b9d2683bfec48cef246075ef912d35a84aabedb9d72723ccc48a9bd0240ef39

Tx prefix hash: 22a62dc5984771aa7ccb9d7dd5e0f276d8f985985634f8942f723d6d91de6aa1
Tx public key: 954e7859d71615625c6bd481f86daa20f00c863e5457016d550b957ba97bf2a5
Timestamp: 1710873565 Timestamp [UCT]: 2024-03-19 18:39:25 Age [y:d:h:m:s]: 01:000:14:30:30
Block: 981915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261408 RingCT/type: yes/0
Extra: 01954e7859d71615625c6bd481f86daa20f00c863e5457016d550b957ba97bf2a502110000000a52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcfa4b915bfc1bac7bcb5cbfc2cf5bbe7e718dfd20ceba70d70a4a651633a5a0 0.600000000000 1442018 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": 981925, "vin": [ { "gen": { "height": 981915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcfa4b915bfc1bac7bcb5cbfc2cf5bbe7e718dfd20ceba70d70a4a651633a5a0" } } ], "extra": [ 1, 149, 78, 120, 89, 215, 22, 21, 98, 92, 107, 212, 129, 248, 109, 170, 32, 240, 12, 134, 62, 84, 87, 1, 109, 85, 11, 149, 123, 169, 123, 242, 165, 2, 17, 0, 0, 0, 10, 82, 212, 126, 148, 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