Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfbfb69e6ce65aa19a2d5de0bce11d569723690aa8fcfe0ed011f8523e4d6afd

Tx prefix hash: bd2f0d52459ec788dce61d52daa502b3b50e4603a4a18cca6cdf69a8d05893ad
Tx public key: f188a2a9f0dcc070c2eaf53eb09aaba8de1d4bab552fb86ba69fb82a429c460c
Timestamp: 1734057227 Timestamp [UCT]: 2024-12-13 02:33:47 Age [y:d:h:m:s]: 00:097:09:10:01
Block: 1174007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69391 RingCT/type: yes/0
Extra: 01f188a2a9f0dcc070c2eaf53eb09aaba8de1d4bab552fb86ba69fb82a429c460c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ec9afd9193ee2d825ffa1bc89b0b7717886496fbd51af38a4988782cdaa2294 0.600000000000 1660104 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": 1174017, "vin": [ { "gen": { "height": 1174007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ec9afd9193ee2d825ffa1bc89b0b7717886496fbd51af38a4988782cdaa2294" } } ], "extra": [ 1, 241, 136, 162, 169, 240, 220, 192, 112, 194, 234, 245, 62, 176, 154, 171, 168, 222, 29, 75, 171, 85, 47, 184, 107, 166, 159, 184, 42, 66, 156, 70, 12, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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