Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667beb2c88b3c93934782d4de08f099f35c88c2e57cbef3e66ec7e6f82823d4d

Tx prefix hash: 503fec6b64b4031b0c98975c4c34a0a65dc09008dc2c01fcab64bfa31397158d
Tx public key: 87540b1fb38719dca7108c7f2d39ec0eceec4e4d1d367dd378e828a3b2165ed1
Timestamp: 1648270551 Timestamp [UCT]: 2022-03-26 04:55:51 Age [y:d:h:m:s]: 03:022:14:03:38
Block: 466579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 796318 RingCT/type: yes/0
Extra: 0187540b1fb38719dca7108c7f2d39ec0eceec4e4d1d367dd378e828a3b2165ed10211000000034a0f5013000000000000000000

1 output(s) for total of 17.459441264000 dcy

stealth address amount amount idx
00: 00ed8527fe80f65ed22757b35d8e0fcccf93f162ea40436ed0db42896de8a838 17.459441264000 884918 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": 466589, "vin": [ { "gen": { "height": 466579 } } ], "vout": [ { "amount": 17459441264, "target": { "key": "00ed8527fe80f65ed22757b35d8e0fcccf93f162ea40436ed0db42896de8a838" } } ], "extra": [ 1, 135, 84, 11, 31, 179, 135, 25, 220, 167, 16, 140, 127, 45, 57, 236, 14, 206, 236, 78, 77, 29, 54, 125, 211, 120, 232, 40, 163, 178, 22, 94, 209, 2, 17, 0, 0, 0, 3, 74, 15, 80, 19, 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