Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00f6e550421dd86d38f2b7814e448ae86ab8796b20720e96cd58b7a02b495c1f

Tx prefix hash: 3c97c7f9735563bcb811f20caa8c040e6f9fa026f5d886a738b12f1c793ba1b1
Tx public key: 3440db3953ebb4123dd8f1776eaa19261cceede0c023be0e89677d0995c5c6d4
Timestamp: 1727097763 Timestamp [UCT]: 2024-09-23 13:22:43 Age [y:d:h:m:s]: 00:218:04:22:52
Block: 1116402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155772 RingCT/type: yes/0
Extra: 013440db3953ebb4123dd8f1776eaa19261cceede0c023be0e89677d0995c5c6d4021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 713c355c9182539a4377ec54d7a353de99af0edc3d6c01286f8b1e73d3a8e489 0.600000000000 1596869 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": 1116412, "vin": [ { "gen": { "height": 1116402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "713c355c9182539a4377ec54d7a353de99af0edc3d6c01286f8b1e73d3a8e489" } } ], "extra": [ 1, 52, 64, 219, 57, 83, 235, 180, 18, 61, 216, 241, 119, 110, 170, 25, 38, 28, 206, 237, 224, 192, 35, 190, 14, 137, 103, 125, 9, 149, 197, 198, 212, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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