Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fc88874bd75680899a6c901088eeed0c3bc3068c3786bfc4af31da0cc9bab2b

Tx prefix hash: 504720feb2723c815f7861106745dce2e3339ac61d82c5f6f4e9ffe31d809d79
Tx public key: f7b5300fdaa7cba259fe32d6714224c456e5d1fe9d3b94e6fcce44dc0fef1d10
Timestamp: 1643620762 Timestamp [UCT]: 2022-01-31 09:19:22 Age [y:d:h:m:s]: 03:137:04:03:41
Block: 429098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 877158 RingCT/type: yes/0
Extra: 01f7b5300fdaa7cba259fe32d6714224c456e5d1fe9d3b94e6fcce44dc0fef1d10021100000001bf7ee4e7000000000000000000

1 output(s) for total of 23.239164404000 dcy

stealth address amount amount idx
00: a1f24a5563d9b97eef0f2d4b8684310be3f9a16b9ca875f5ea7d0d2ef79b76d4 23.239164404000 838666 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": 429108, "vin": [ { "gen": { "height": 429098 } } ], "vout": [ { "amount": 23239164404, "target": { "key": "a1f24a5563d9b97eef0f2d4b8684310be3f9a16b9ca875f5ea7d0d2ef79b76d4" } } ], "extra": [ 1, 247, 181, 48, 15, 218, 167, 203, 162, 89, 254, 50, 214, 113, 66, 36, 196, 86, 229, 209, 254, 157, 59, 148, 230, 252, 206, 68, 220, 15, 239, 29, 16, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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