Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bde1e11856550624a55bf33ec2fc2cf2ba976238be96159346ed1b35b57f59ba

Tx prefix hash: f4ac130aee8c6a26639f840f72ddbca50fe703bc7a16b1125feec4c4c7f0da58
Tx public key: aad19b1f5bdaccc0bfb2a2593779bdd2c0e8cf7bc7ed033be1f80bd24f46c70d
Timestamp: 1703294199 Timestamp [UCT]: 2023-12-23 01:16:39 Age [y:d:h:m:s]: 01:099:12:20:28
Block: 919053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332244 RingCT/type: yes/0
Extra: 01aad19b1f5bdaccc0bfb2a2593779bdd2c0e8cf7bc7ed033be1f80bd24f46c70d0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc8a8f0c593c18853cfb7d10097f63a45ef4c58465b603f51db686743ef96818 0.600000000000 1376717 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": 919063, "vin": [ { "gen": { "height": 919053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc8a8f0c593c18853cfb7d10097f63a45ef4c58465b603f51db686743ef96818" } } ], "extra": [ 1, 170, 209, 155, 31, 91, 218, 204, 192, 191, 178, 162, 89, 55, 121, 189, 210, 192, 232, 207, 123, 199, 237, 3, 59, 225, 248, 11, 210, 79, 70, 199, 13, 2, 17, 0, 0, 0, 9, 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