Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fe5367cb32e9d005a27ce7e430ae838bce2c3395ca6a792fd066abb9a21ec30

Tx prefix hash: 33ff3311e407fe7547b027370e1e4e19c551f607a1c48d6c5097520ba445e8e5
Tx public key: 796d28520edbe9dd7c9685606d52a4b7ccd209d7779e46ec5d46a7ea04af5080
Timestamp: 1723393706 Timestamp [UCT]: 2024-08-11 16:28:26 Age [y:d:h:m:s]: 01:092:22:11:55
Block: 1085691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324889 RingCT/type: yes/0
Extra: 01796d28520edbe9dd7c9685606d52a4b7ccd209d7779e46ec5d46a7ea04af508002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 921f3aaaedd03a3896fcf94c5593e89d23badc7e69e3d7444ae05a7264bb35b5 0.600000000000 1560280 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": 1085701, "vin": [ { "gen": { "height": 1085691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "921f3aaaedd03a3896fcf94c5593e89d23badc7e69e3d7444ae05a7264bb35b5" } } ], "extra": [ 1, 121, 109, 40, 82, 14, 219, 233, 221, 124, 150, 133, 96, 109, 82, 164, 183, 204, 210, 9, 215, 119, 158, 70, 236, 93, 70, 167, 234, 4, 175, 80, 128, 2, 17, 0, 0, 0, 1, 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