Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f8dd42b091a74f276c2250191afdcf83bdf474a3d41a928ba0645f63011173

Tx prefix hash: c1c4d15a3ed75c81e640974e820660ea9ad6a389e9c8f2cdaa40a47fddcec2ce
Tx public key: 5af3f590214429f24f2bbc1af8a7b3b59be82db322f9f6f312857da2605c1540
Timestamp: 1710011385 Timestamp [UCT]: 2024-03-09 19:09:45 Age [y:d:h:m:s]: 01:032:03:54:50
Block: 974753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283974 RingCT/type: yes/0
Extra: 015af3f590214429f24f2bbc1af8a7b3b59be82db322f9f6f312857da2605c15400211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eb9a7c54cbd772df0279487b7deb5821d30c8759912e426aa8454af94859828 0.600000000000 1434712 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": 974763, "vin": [ { "gen": { "height": 974753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eb9a7c54cbd772df0279487b7deb5821d30c8759912e426aa8454af94859828" } } ], "extra": [ 1, 90, 243, 245, 144, 33, 68, 41, 242, 79, 43, 188, 26, 248, 167, 179, 181, 155, 232, 45, 179, 34, 249, 246, 243, 18, 133, 125, 162, 96, 92, 21, 64, 2, 17, 0, 0, 0, 3, 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