Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1743cfec62fbe6844e3f93ae963380da5abc3c8fea9c0709709b4637a826dd8

Tx prefix hash: 5619085ab4c4179d5655ee15229b6f29a0c774768dac971e4a1c51c9481fb907
Tx public key: fa1e04fbfb051adbc343b70cd3f48ab444bfc508f85776465d5d7761f135039d
Timestamp: 1725972721 Timestamp [UCT]: 2024-09-10 12:52:01 Age [y:d:h:m:s]: 00:225:11:51:21
Block: 1107075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160994 RingCT/type: yes/0
Extra: 01fa1e04fbfb051adbc343b70cd3f48ab444bfc508f85776465d5d7761f135039d021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 535c96129894b0e07fbd3ed66a927e2c87b9c4c2f2e087fdab7011da323f2616 0.600000000000 1584682 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": 1107085, "vin": [ { "gen": { "height": 1107075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "535c96129894b0e07fbd3ed66a927e2c87b9c4c2f2e087fdab7011da323f2616" } } ], "extra": [ 1, 250, 30, 4, 251, 251, 5, 26, 219, 195, 67, 183, 12, 211, 244, 138, 180, 68, 191, 197, 8, 248, 87, 118, 70, 93, 93, 119, 97, 241, 53, 3, 157, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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