Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 955ea4805fea3fec21540c1e4f227a3c413208b183f078d91bd19236327084c8

Tx prefix hash: 8cec00ac6ec3aff1aa077ebb61a05c99d0163be0e97b90f5be9a31c7db5c629f
Tx public key: f493676a2e3b1f71feda48c4a13b9708aa6e74c797d3c26d0330744c5ca3ce4c
Timestamp: 1704817041 Timestamp [UCT]: 2024-01-09 16:17:21 Age [y:d:h:m:s]: 01:048:07:25:32
Block: 931668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295597 RingCT/type: yes/0
Extra: 01f493676a2e3b1f71feda48c4a13b9708aa6e74c797d3c26d0330744c5ca3ce4c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4952318ee7a6aa55b996e787005c69327fcbcf71b7985995acbfc1dc6c2d3498 0.600000000000 1389572 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": 931678, "vin": [ { "gen": { "height": 931668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4952318ee7a6aa55b996e787005c69327fcbcf71b7985995acbfc1dc6c2d3498" } } ], "extra": [ 1, 244, 147, 103, 106, 46, 59, 31, 113, 254, 218, 72, 196, 161, 59, 151, 8, 170, 110, 116, 199, 151, 211, 194, 109, 3, 48, 116, 76, 92, 163, 206, 76, 2, 17, 0, 0, 0, 3, 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