Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f8be2b15db22f8a8cda94a59165073965cfbbbad2d864ab2d3dd73c785b77f9

Tx prefix hash: bf3a998295dfefdf90d691d00a8d73ce7d6abdc925e1537b7ed738dfe87b38a5
Tx public key: 6679bd4e0382ea2be4decda45c7d9a85bc6d37ce5e4cd7d61ef8311e62c6e781
Timestamp: 1713986940 Timestamp [UCT]: 2024-04-24 19:29:00 Age [y:d:h:m:s]: 01:020:16:32:51
Block: 1007703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275738 RingCT/type: yes/0
Extra: 016679bd4e0382ea2be4decda45c7d9a85bc6d37ce5e4cd7d61ef8311e62c6e7810211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea2023c2cee232b3ea227c202cfc688aeaa3e7255a6e42c5cb0f87889decf1b3 0.600000000000 1469131 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": 1007713, "vin": [ { "gen": { "height": 1007703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea2023c2cee232b3ea227c202cfc688aeaa3e7255a6e42c5cb0f87889decf1b3" } } ], "extra": [ 1, 102, 121, 189, 78, 3, 130, 234, 43, 228, 222, 205, 164, 92, 125, 154, 133, 188, 109, 55, 206, 94, 76, 215, 214, 30, 248, 49, 30, 98, 198, 231, 129, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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