Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dbade132a2b276d992d6539ad92082b07828045ba908232acece70c1c9e893d

Tx prefix hash: 5206d16ba2c3666cdf1b043b42e8fe87927bacd235931af6e8f6ea1b16b30ceb
Tx public key: 146dac52bd2401498a010b699e9f5557b6bc75faee4e86b326e5716e49bec4e6
Timestamp: 1719256324 Timestamp [UCT]: 2024-06-24 19:12:04 Age [y:d:h:m:s]: 00:285:17:09:37
Block: 1051377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204166 RingCT/type: yes/0
Extra: 01146dac52bd2401498a010b699e9f5557b6bc75faee4e86b326e5716e49bec4e6021100000005a6fba9af000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd050368b9fc584a48d1f32e5daee96a520c77a045b996e7a9a0b35a6349f526 0.600000000000 1521688 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": 1051387, "vin": [ { "gen": { "height": 1051377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd050368b9fc584a48d1f32e5daee96a520c77a045b996e7a9a0b35a6349f526" } } ], "extra": [ 1, 20, 109, 172, 82, 189, 36, 1, 73, 138, 1, 11, 105, 158, 159, 85, 87, 182, 188, 117, 250, 238, 78, 134, 179, 38, 229, 113, 110, 73, 190, 196, 230, 2, 17, 0, 0, 0, 5, 166, 251, 169, 175, 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