Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03a570bc5b1bebeeb0cb97e0e5208cd26dc22dea75d3cc643ad200b4a139120b

Tx prefix hash: 95e4dc945a07081562ae88f183c54e993c64299d9fc0abe48f0b62d33f8e7bf7
Tx public key: 2cd40aed4332bf647941eb9c381cce3b73973bb59df3a839b207e9803fef9a3a
Timestamp: 1723596496 Timestamp [UCT]: 2024-08-14 00:48:16 Age [y:d:h:m:s]: 00:254:00:32:26
Block: 1087376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181438 RingCT/type: yes/0
Extra: 012cd40aed4332bf647941eb9c381cce3b73973bb59df3a839b207e9803fef9a3a02110000001491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 043f268c56c7c2ec192cf741ea03a9b430b820823875a76d107ee24012896a48 0.600000000000 1561985 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": 1087386, "vin": [ { "gen": { "height": 1087376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "043f268c56c7c2ec192cf741ea03a9b430b820823875a76d107ee24012896a48" } } ], "extra": [ 1, 44, 212, 10, 237, 67, 50, 191, 100, 121, 65, 235, 156, 56, 28, 206, 59, 115, 151, 59, 181, 157, 243, 168, 57, 178, 7, 233, 128, 63, 239, 154, 58, 2, 17, 0, 0, 0, 20, 145, 225, 60, 4, 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