Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41fed4bd298e2cf37d59ab69136f0a252d5e7bb83fa1856feeb0b6096b4bafc3

Tx prefix hash: ef8a5578ad43ecb70144e65d0e65521db371591e35035666264d11d41b1a8969
Tx public key: a6a7f9c6dbbc814da593a9d2c346ace8d0e652db15b7d83ebf0d2db1004ab2b2
Timestamp: 1713131322 Timestamp [UCT]: 2024-04-14 21:48:42 Age [y:d:h:m:s]: 00:356:18:04:32
Block: 1000590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255058 RingCT/type: yes/0
Extra: 01a6a7f9c6dbbc814da593a9d2c346ace8d0e652db15b7d83ebf0d2db1004ab2b20211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa3e71cfabd6060bbbbc74cb24330138e4a20a90849bfea75ac9497ca34c88df 0.600000000000 1461088 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": 1000600, "vin": [ { "gen": { "height": 1000590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa3e71cfabd6060bbbbc74cb24330138e4a20a90849bfea75ac9497ca34c88df" } } ], "extra": [ 1, 166, 167, 249, 198, 219, 188, 129, 77, 165, 147, 169, 210, 195, 70, 172, 232, 208, 230, 82, 219, 21, 183, 216, 62, 191, 13, 45, 177, 0, 74, 178, 178, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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