Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f826d34f1e2c674c27250008721b738ec927fa4e279ed9c045cff842b180466

Tx prefix hash: 8931e0f54fa7a7f1ed7658d3fef96fa21c2f8f0c1416422bbefd20f71ee7889a
Tx public key: a33fde1b91632cd877aa6f13277f8f5e1b53e59640adb914e3b6939eda039790
Timestamp: 1707749274 Timestamp [UCT]: 2024-02-12 14:47:54 Age [y:d:h:m:s]: 01:012:19:34:38
Block: 955980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270177 RingCT/type: yes/0
Extra: 01a33fde1b91632cd877aa6f13277f8f5e1b53e59640adb914e3b6939eda0397900211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16731f25aa2b9e99d47dcc790264eb9c3da3e5c64c0acb3e2c247e66753eea09 0.600000000000 1415282 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": 955990, "vin": [ { "gen": { "height": 955980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16731f25aa2b9e99d47dcc790264eb9c3da3e5c64c0acb3e2c247e66753eea09" } } ], "extra": [ 1, 163, 63, 222, 27, 145, 99, 44, 216, 119, 170, 111, 19, 39, 127, 143, 94, 27, 83, 229, 150, 64, 173, 185, 20, 227, 182, 147, 158, 218, 3, 151, 144, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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