Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61590e0b80909039d0a8c5ed78433467655e64c3a835a47ea30e7da98725a59b

Tx prefix hash: 39e0ff55b26f99ca7905e780c060b45db7abac2580f712ae6d933aef12eb78f7
Tx public key: f7254de95c7d417f306d96e32a9895e00879dfccfef2e816a242b3f43e32ec84
Timestamp: 1735022179 Timestamp [UCT]: 2024-12-24 06:36:19 Age [y:d:h:m:s]: 00:100:02:04:04
Block: 1181983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71308 RingCT/type: yes/0
Extra: 01f7254de95c7d417f306d96e32a9895e00879dfccfef2e816a242b3f43e32ec840211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ccb2c890005bda9ae936e49249ab09646b603b9d6eb4e19357b059423f5fe47 0.600000000000 1668412 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": 1181993, "vin": [ { "gen": { "height": 1181983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ccb2c890005bda9ae936e49249ab09646b603b9d6eb4e19357b059423f5fe47" } } ], "extra": [ 1, 247, 37, 77, 233, 92, 125, 65, 127, 48, 109, 150, 227, 42, 152, 149, 224, 8, 121, 223, 204, 254, 242, 232, 22, 162, 66, 179, 244, 62, 50, 236, 132, 2, 17, 0, 0, 0, 6, 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