Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b05be30a4961aa07f04b8a5a3fff9cf620010336ba39a44f3d5606eec9ddb12d

Tx prefix hash: 63fcfae8ae2714f337ff0b72539fe5987fa2b54fae2675f0c6940fb4879edf61
Tx public key: fee50fe966c481efbcbf815e962ba1e55dcb3ef2d3a6fd50fdd7fcaf90244c52
Timestamp: 1706618932 Timestamp [UCT]: 2024-01-30 12:48:52 Age [y:d:h:m:s]: 00:327:08:02:33
Block: 946596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234407 RingCT/type: yes/0
Extra: 01fee50fe966c481efbcbf815e962ba1e55dcb3ef2d3a6fd50fdd7fcaf90244c5202110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f01c6c55ef97112013db594f0a2526dc5e2b5cf77dae7b13d7b81ccf4994740 0.600000000000 1404928 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": 946606, "vin": [ { "gen": { "height": 946596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f01c6c55ef97112013db594f0a2526dc5e2b5cf77dae7b13d7b81ccf4994740" } } ], "extra": [ 1, 254, 229, 15, 233, 102, 196, 129, 239, 188, 191, 129, 94, 150, 43, 161, 229, 93, 203, 62, 242, 211, 166, 253, 80, 253, 215, 252, 175, 144, 36, 76, 82, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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