Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a47a66803b507cd695964164693cbb797c8d59ee48ab78364f0fa61a6153ca

Tx prefix hash: 53bdb2969fa0b9b0a698c0879bfe3174bdbf4cf0445e00bf4230c9a9609d6b3d
Tx public key: 9fd9f7593a44d75d0d9fd5728c6ff500c5cf261b073d289292d78f9709c4ca71
Timestamp: 1729545840 Timestamp [UCT]: 2024-10-21 21:24:00 Age [y:d:h:m:s]: 00:227:00:18:06
Block: 1136651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162102 RingCT/type: yes/0
Extra: 019fd9f7593a44d75d0d9fd5728c6ff500c5cf261b073d289292d78f9709c4ca71021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f882984a350ee09ac3f3492a6a4cce87b8c35763ed51e85fade217c7188a619 0.600000000000 1619998 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": 1136661, "vin": [ { "gen": { "height": 1136651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f882984a350ee09ac3f3492a6a4cce87b8c35763ed51e85fade217c7188a619" } } ], "extra": [ 1, 159, 217, 247, 89, 58, 68, 215, 93, 13, 159, 213, 114, 140, 111, 245, 0, 197, 207, 38, 27, 7, 61, 40, 146, 146, 215, 143, 151, 9, 196, 202, 113, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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