Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffa75f865f0d074a8b495cacd92b98126cb5c16890c84c9d23a7ccbabac4d11

Tx prefix hash: 0e88d41f3b71280def15f273524a14c96f140139f74ad7f4e71a7137563ae083
Tx public key: 4f581ef4a2b31c0160c11ad2823c2ce9234ab1bf73d67025ce3b4ddc9f13e904
Timestamp: 1729599419 Timestamp [UCT]: 2024-10-22 12:16:59 Age [y:d:h:m:s]: 00:032:19:15:26
Block: 1137102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 23437 RingCT/type: yes/0
Extra: 014f581ef4a2b31c0160c11ad2823c2ce9234ab1bf73d67025ce3b4ddc9f13e904021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1895fac1f5fe37304eb3d896c6d59975f6f80061df2e0879e76940414b3bed90 0.600000000000 1620531 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": 1137112, "vin": [ { "gen": { "height": 1137102 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1895fac1f5fe37304eb3d896c6d59975f6f80061df2e0879e76940414b3bed90" } } ], "extra": [ 1, 79, 88, 30, 244, 162, 179, 28, 1, 96, 193, 26, 210, 130, 60, 44, 233, 35, 74, 177, 191, 115, 214, 112, 37, 206, 59, 77, 220, 159, 19, 233, 4, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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