Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34e165c7c1830836d8c01dcb3d72fba23fd20b1ac056cdaa6e412c252d6431bf

Tx prefix hash: 6cbe700aaef0c4294c84887737bbd3315708a8bbbc316cea0086271ae08e4191
Tx public key: ff992c92add383f20ae217da3ab189ec1901d719f86b7a5d82f272ae7d138f95
Timestamp: 1705328191 Timestamp [UCT]: 2024-01-15 14:16:31 Age [y:d:h:m:s]: 01:041:06:54:31
Block: 935903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290571 RingCT/type: yes/0
Extra: 01ff992c92add383f20ae217da3ab189ec1901d719f86b7a5d82f272ae7d138f950211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1cc4ffa9e3a15750a91eed5babd12fd17641aafdbf146f4834aa8dfa720fba3 0.600000000000 1393921 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": 935913, "vin": [ { "gen": { "height": 935903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1cc4ffa9e3a15750a91eed5babd12fd17641aafdbf146f4834aa8dfa720fba3" } } ], "extra": [ 1, 255, 153, 44, 146, 173, 211, 131, 242, 10, 226, 23, 218, 58, 177, 137, 236, 25, 1, 215, 25, 248, 107, 122, 93, 130, 242, 114, 174, 125, 19, 143, 149, 2, 17, 0, 0, 0, 4, 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