Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d7594eeb579967bdc9c65f0230ff63727198056c60f86431c68ab2f86254e4e

Tx prefix hash: d8b9089c999856fee4b05e433d32c61af9daf3a26670d57a3d88a395ed283b80
Tx public key: d5d9530caa7c407ae992eaee4c52d539e0e7a85b9d0f6f52554b3878a3b004b0
Timestamp: 1632788329 Timestamp [UCT]: 2021-09-28 00:18:49 Age [y:d:h:m:s]: 02:281:01:59:28
Block: 342153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 716603 RingCT/type: yes/0
Extra: 01d5d9530caa7c407ae992eaee4c52d539e0e7a85b9d0f6f52554b3878a3b004b00211000000095410958b000000000000000000

1 output(s) for total of 45.113394691000 dcy

stealth address amount amount idx
00: ea10a82f46537b88ca28941cb8da8ed5ae105c4df4795e69da4260b78b2b0a01 45.113394691000 702713 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": 342163, "vin": [ { "gen": { "height": 342153 } } ], "vout": [ { "amount": 45113394691, "target": { "key": "ea10a82f46537b88ca28941cb8da8ed5ae105c4df4795e69da4260b78b2b0a01" } } ], "extra": [ 1, 213, 217, 83, 12, 170, 124, 64, 122, 233, 146, 234, 238, 76, 82, 213, 57, 224, 231, 168, 91, 157, 15, 111, 82, 85, 75, 56, 120, 163, 176, 4, 176, 2, 17, 0, 0, 0, 9, 84, 16, 149, 139, 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