Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf060d3f25e2b90b29449c58ee596b72caeeb5622072f2558b34a074bc58f2b6

Tx prefix hash: 4dbf57d7d110df74bb63c9e18068692ef34ec77a556ce587b7ec361ad80b0599
Tx public key: f48f0beb53b0ee4a2a20c592bffa5465e062e6a14bb163508e562b5b68094509
Timestamp: 1732480502 Timestamp [UCT]: 2024-11-24 20:35:02 Age [y:d:h:m:s]: 00:131:05:30:47
Block: 1160931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93593 RingCT/type: yes/0
Extra: 01f48f0beb53b0ee4a2a20c592bffa5465e062e6a14bb163508e562b5b6809450902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e53f39e1e77904befc38cfd811092a950fd90e1f8dcb52b19d5696fd9090cbd6 0.600000000000 1646582 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": 1160941, "vin": [ { "gen": { "height": 1160931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e53f39e1e77904befc38cfd811092a950fd90e1f8dcb52b19d5696fd9090cbd6" } } ], "extra": [ 1, 244, 143, 11, 235, 83, 176, 238, 74, 42, 32, 197, 146, 191, 250, 84, 101, 224, 98, 230, 161, 75, 177, 99, 80, 142, 86, 43, 91, 104, 9, 69, 9, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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