Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f0783e967d959045130ea7b76c65aabd0c34bc7206df69544777c367e9b7af2

Tx prefix hash: b577549a125a5501b1e750c1a70c4c65e1a6b0da4ec51163c05b20d622eafab5
Tx public key: 74391fea0def46beacfccaae93a52ecb71b7b93d67515d8dc3286bb3e259c44a
Timestamp: 1730044529 Timestamp [UCT]: 2024-10-27 15:55:29 Age [y:d:h:m:s]: 00:097:17:50:55
Block: 1140793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69613 RingCT/type: yes/0
Extra: 0174391fea0def46beacfccaae93a52ecb71b7b93d67515d8dc3286bb3e259c44a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b5558a76e244f749c785a108e0492590aa1c5621ae7c82178418d7f49d76bfc 0.600000000000 1624596 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": 1140803, "vin": [ { "gen": { "height": 1140793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b5558a76e244f749c785a108e0492590aa1c5621ae7c82178418d7f49d76bfc" } } ], "extra": [ 1, 116, 57, 31, 234, 13, 239, 70, 190, 172, 252, 202, 174, 147, 165, 46, 203, 113, 183, 185, 61, 103, 81, 93, 141, 195, 40, 107, 179, 226, 89, 196, 74, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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