Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb391023aa6322d14003e7534d8fed68ebcebb5ec36958818a37d39583c484a0

Tx prefix hash: d2e25e1128d90e1c3c7f8ca2ed6887ef7772a0ca50ae165d01afba8477c969e2
Tx public key: 3897c9beb0e9fc165944814f7df3a3dc2c76369db2b092a8d686f016db78fe56
Timestamp: 1730398080 Timestamp [UCT]: 2024-10-31 18:08:00 Age [y:d:h:m:s]: 00:175:20:19:54
Block: 1143680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125530 RingCT/type: yes/0
Extra: 013897c9beb0e9fc165944814f7df3a3dc2c76369db2b092a8d686f016db78fe5602110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29cdb20f814340ad7a17fd7e0a179cc703188dc22a6ee5e02b2375841e3a8dfb 0.600000000000 1627633 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": 1143690, "vin": [ { "gen": { "height": 1143680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29cdb20f814340ad7a17fd7e0a179cc703188dc22a6ee5e02b2375841e3a8dfb" } } ], "extra": [ 1, 56, 151, 201, 190, 176, 233, 252, 22, 89, 68, 129, 79, 125, 243, 163, 220, 44, 118, 54, 157, 178, 176, 146, 168, 214, 134, 240, 22, 219, 120, 254, 86, 2, 17, 0, 0, 0, 11, 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