Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfce3c76e6f0f01fb872025997efbf70f50723d8ecbc20acd927cbfabd7bc434

Tx prefix hash: 643d3ac86c8872502a484309815c4082f7e63b66132aa19e366f2ff9eb4c2fdf
Tx public key: eff328353b03eea97f8f7dde3ff932bdc93dfeeb07e4e6c25f570c735df03d34
Timestamp: 1721741916 Timestamp [UCT]: 2024-07-23 13:38:36 Age [y:d:h:m:s]: 00:333:00:40:17
Block: 1071985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237821 RingCT/type: yes/0
Extra: 01eff328353b03eea97f8f7dde3ff932bdc93dfeeb07e4e6c25f570c735df03d3402110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e488b600820e24fbc9559f352b9c686c8cc42f3cd436d284c9cf30c2a59eeaa 0.600000000000 1544400 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": 1071995, "vin": [ { "gen": { "height": 1071985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e488b600820e24fbc9559f352b9c686c8cc42f3cd436d284c9cf30c2a59eeaa" } } ], "extra": [ 1, 239, 243, 40, 53, 59, 3, 238, 169, 127, 143, 125, 222, 63, 249, 50, 189, 201, 61, 254, 235, 7, 228, 230, 194, 95, 87, 12, 115, 93, 240, 61, 52, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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