Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4fef8b424389ac1b5c895c19e774286aa19af363510a6a7ec06fc227e83eac3

Tx prefix hash: cf63f7c3b66ca9d58081c5dccfc33832534c9d9fc42a9e95a6659bedb8356f61
Tx public key: 40259e78e8cf8e635f647f7e5924823068c8b99faa90420c3ead73464a4ae2e9
Timestamp: 1675164470 Timestamp [UCT]: 2023-01-31 11:27:50 Age [y:d:h:m:s]: 02:104:06:25:14
Block: 686722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 596187 RingCT/type: yes/0
Extra: 0140259e78e8cf8e635f647f7e5924823068c8b99faa90420c3ead73464a4ae2e90211000000035029cbac000000000000000000

1 output(s) for total of 3.255403866000 dcy

stealth address amount amount idx
00: 89f16addebcd7e0fff3fb73ce468654005ffffe725e716eb2d28394c48c6f8b0 3.255403866000 1129252 of 0

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": 686732, "vin": [ { "gen": { "height": 686722 } } ], "vout": [ { "amount": 3255403866, "target": { "key": "89f16addebcd7e0fff3fb73ce468654005ffffe725e716eb2d28394c48c6f8b0" } } ], "extra": [ 1, 64, 37, 158, 120, 232, 207, 142, 99, 95, 100, 127, 126, 89, 36, 130, 48, 104, 200, 185, 159, 170, 144, 66, 12, 62, 173, 115, 70, 74, 74, 226, 233, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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