Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6804a60a1481c6554b7cb28bb8339293b0d52c226175e409cabea50ea5e5008a

Tx prefix hash: 469e9f3e120b69f720e7b68fbe322991b4b5404db28f24b3e5f1c10894b511e7
Tx public key: 752d8bbd9bde1ee6c806dcc18bf8490d11f42da5a0c73ccfb09282e15fed1add
Timestamp: 1686296822 Timestamp [UCT]: 2023-06-09 07:47:02 Age [y:d:h:m:s]: 01:159:17:37:08
Block: 778397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375514 RingCT/type: yes/0
Extra: 01752d8bbd9bde1ee6c806dcc18bf8490d11f42da5a0c73ccfb09282e15fed1add02110000000475e3f0e9000000000000000000

1 output(s) for total of 1.617512973000 dcy

stealth address amount amount idx
00: 1d585c8a10e4f4898806e16e30b944f558a531972c0baae159a9d4eddaf7af60 1.617512973000 1228020 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": 778407, "vin": [ { "gen": { "height": 778397 } } ], "vout": [ { "amount": 1617512973, "target": { "key": "1d585c8a10e4f4898806e16e30b944f558a531972c0baae159a9d4eddaf7af60" } } ], "extra": [ 1, 117, 45, 139, 189, 155, 222, 30, 230, 200, 6, 220, 193, 139, 248, 73, 13, 17, 244, 45, 165, 160, 199, 60, 207, 176, 146, 130, 225, 95, 237, 26, 221, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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